Run tests and rule validation in CI#3
Merged
NicholasEllul merged 1 commit intoellul/initfrom Jan 20, 2025
Merged
Conversation
98a754a to
563073b
Compare
165f3ae to
be89eb7
Compare
563073b to
43cd2c8
Compare
witmicko
approved these changes
Jan 17, 2025
d238078 to
43cd2c8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This pull request adds a GitHub workflow that will run Semgrep rule validation and Semgrep tests in CI. This will help ensure the rules we are developing are vetted prior to merge.
Testing
rules/src/directory that breaks the config file in some way (e.g renamepatterntopatern)bin/validate-rulesand see that it gets flagged.Example output
rules/testdirectory such that one of the lines flagging a rule (which look like -->ruleid: publish-actions-cache-used), is renamed to# ok: publish-actions-cache-used.Example output